Correcting erroneous timeline. #1
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
First of all, I wanted to re-extend our thanks for your report.
However, I wanted to make sure the timeline was set correctly. Our records indicate Cloudbees received it on May 05, hence this PR. The Jenkins project should not be confused with Cloudbees commercial products.
In the future, in the event you report further findings to Cloudbees, we would appreciate you to check https://www.cloudbees.com/security-policy or simply send an email to security@cloudbees.com so that we can handle your finding with the proper care.
Thank you.
Best,